home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20020314-20021006
/
000157_fdc@columbia.edu_Thu Jun 13 09:59:39 EDT 2002.msg
< prev
next >
Wrap
Text File
|
2020-01-01
|
2KB
|
53 lines
Article: 13458 of comp.protocols.kermit.misc
Path: newsmaster.cc.columbia.edu!news.columbia.edu!news-not-for-mail
From: fdc@columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: how autostart kermit 95 server after remote command.
Date: 13 Jun 2002 09:59:30 -0400
Organization: Columbia University
Lines: 36
Message-ID: <aea8g2$ju7$1@watsol.cc.columbia.edu>
References: <Pq0O8.5$124.1860@wwwserv3.shell.nl>
NNTP-Posting-Host: watsol.cc.columbia.edu
X-Trace: newsmaster.cc.columbia.edu 1023976771 19496 128.59.39.139 (13 Jun 2002 13:59:31 GMT)
X-Complaints-To: postmaster@columbia.edu
NNTP-Posting-Date: 13 Jun 2002 13:59:31 GMT
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:13458
In article <Pq0O8.5$124.1860@wwwserv3.shell.nl>,
Eddie <Edreset@REMOVEMEhotmail.com> wrote:
: We were previously using a kermit server on VAX/VMS systems. Due the phse
: out of these vaxes we need a replacement for the kermit server.
:
: We ordered kermit 95 and installed it on a NT server.
:
: Now we discoverded that the remote computer sends after login a "KERMIT
: SERVER" string to startup the kermit server on the vaxes
:
: Because the remote machine is a process machine we prefer nothing to change
: at it.
:
: Thus i like to know how I can make script wherin after receiving the string
: the server part of kermit start automaticly.
:
By now you have realized that VMS and NT are radically different platforms.
VMS lets people come in by various methods (serial port, dialup, Telnet,
LAT, DECnet) and presents them with a DCL prompt so that commands can be
issued and results displayed in an ordinary text window. Starting a Kermit
server on VMS (or Unix, or any other traditional operating system) is
perfectly straightforward -- just type "kermit -x" or whatever.
To do something like this with Windows NT requires at least a Telnet server,
which might be available only from third parties. As for dialing in to get
an NT Command prompt, I don't even know if it's possible.
In any case you can't make such a radical change and expect everything to
work the same way. Of course we'll be glad to help you but you'll need to
tell us how the remote users coming in to NT.
Incidentally, your message suggests you were using Kermit-32, not C-Kermit,
on VMS. Kermit-32 has not been supported since 1987 -- that's two decades
in the past.
- Frank